X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C820AA.E6191850@onstor-exch02.onstor.net>; Tue, 6 Nov 2007 11:26:15 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C820AA.E6191850"
Content-class: urn:content-classes:message
Subject: RE: Reg. quering each node info in a cluster...
Date: Tue, 6 Nov 2007 11:26:13 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E066D1B0D@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E066D18A1@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Reg. quering each node info in a cluster...
Thread-Index: AcggiI7Qzq2DoHQ9QVihHKEpQiNbGQAIZ5Vg
References: <BB375AF679D4A34E9CA8DFA650E2B04E066D18A1@onstor-exch02.onstor.net>
From: "Jonathan Goldick" <jonathan.goldick@onstor.com>
To: "Yuvarani Cothandaraman" <yuvarani.cothandaraman@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>
Cc: "Brian DeForest" <brian.deforest@onstor.com>,
	"Sudharsan Srinivasan" <sudharsan@onstor.com>,
	"Kumar Vakacharla (HCL)" <kumarv@onstor.com>,
	"Prasanna Kumar" <prasanna@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C820AA.E6191850
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Chassisd is not an appropriate choice in my opinion.  It is not an RMC
server intended to service RPC(s) and it would not be a good idea from a
bootstrapping point of view to make it one.  The way commands like
"system show version" use it is by exec'ing it with a command line
option and that is not a solution when you want to run on a remote
filer.

=20

There are plenty of daemons to choose from, too much in fact :-)   VSD
would be an easier choice.

=20

=20

________________________________

From: Yuvarani Cothandaraman=20
Sent: Tuesday, November 06, 2007 7:20 AM
To: dl-Design Review
Cc: Brian DeForest; Sudharsan Srinivasan; Kumar Vakacharla (HCL);
Prasanna Kumar
Subject: Reg. quering each node info in a cluster...

=20

Hi,

   Output for few CLI commands are quite straight forward, say just
reading a file content from that filer.  =20

But when those command support are extended in a cluster environment (to
get each node information), we need a daemon which can service that
request.

=20

We request for inputs/feedback if we can provide this support in
chassisd for the following commands.

=20

1.	"system version" reads the file "/version" (in that filer) to
get the EverON version. While this command is moved to a cluster level,
we need a daemon to service the same during cross-node request. Can this
system specific request be serviced in daemon chassisd? Also to note,
"system show version" is already being serviced in this daemon.=20
2.	New CLI command "system show users", reads the file
"/var/run/utmp" to get the logged in user details ("who" equivalent).
Can this login in specific request also be serviced in chassisd?=20

=20

Thanks & Regards,

Yuva.


------_=_NextPart_001_01C820AA.E6191850
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:157502132;
	mso-list-template-ids:896954738;}
@list l1
	{mso-list-id:1460610365;
	mso-list-type:hybrid;
	mso-list-template-ids:-985228238 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Chassisd is not an appropriate =
choice in
my opinion.&nbsp; It is not an RMC server intended to service RPC(s) and =
it
would not be a good idea from a bootstrapping point of view to make it =
one.&nbsp;
The way commands like &#8220;system show version&#8221; use it is by =
exec&#8217;ing
it with a command line option and that is not a solution when you want =
to run on
a remote filer.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.5in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>There are plenty of daemons to choose from, too much in fact =
</span></font><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'>J</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;&nbsp; VSD =
would be
an easier choice.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.5in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Yuvarani
Cothandaraman <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
06, 2007
7:20 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> dl-Design Review<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Brian DeForest; =
Sudharsan
Srinivasan; Kumar Vakacharla (HCL); Prasanna Kumar<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Reg. quering =
each node
info in a cluster...</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; Output for few CLI commands are quite =
straight
forward, say just reading a file content from that filer.&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>But when those command support are extended in a =
cluster
environment (to get each node information), we need a daemon which can =
service
that request.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>We request for inputs/feedback if we can provide this
support in chassisd for the following =
commands.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<ol style=3D'margin-top:0in' start=3D1 type=3D1>
 <li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo3'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>&#8220;system =
version&#8221;
     reads the file &#8220;/version&#8221; (in that filer) to get the =
EverON
     version. While this command is moved to a cluster level, we need a =
daemon
     to service the same during cross-node request. Can this system =
specific
     request be serviced in daemon chassisd? Also to note, &#8220;system =
show
     version&#8221; is already being serviced in this daemon. =
<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo3'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>New CLI command =
&#8220;system
     show users&#8221;, reads the file &#8220;/var/run/utmp&#8221; to =
get the
     logged in user details (&#8220;who&#8221; equivalent). Can this =
login in
     specific request also be serviced in chassisd? =
<o:p></o:p></span></font></li>
</ol>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks &amp; Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Yuva.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C820AA.E6191850--
